Interfaces for creating radio-based private networks

ABSTRACT

Disclosed are various embodiments for interfaces for creating radio-based private networks. In one embodiment, a request is received via an interface to create a radio-based private network for a customer. The request indicates a quantity of wireless devices that will connect to the radio-based private network. A quantity of radio units to serve the radio-based private network is determined based at least in part on the quantity of wireless devices. The radio units are preconfigured to implement a radio access network for the radio-based private network. A shipment is initiated to the customer of the radio units that have been preconfigured. Resources in a cloud provider network are provisioned to function as a core network for the radio-based private network.

BACKGROUND

5G is the fifth-generation technology standard for broadband cellularnetworks, which is planned eventually to take the place of thefourth-generation (4G) standard of Long-Term Evolution (LTE). 5Gtechnology will offer greatly increased bandwidth, thereby broadeningthe cellular market beyond smartphones to provide last-mile connectivityto desktops, set-top boxes, laptops, Internet of Things (IoT) devices,and so on. Some 5G cells may employ frequency spectrum similar to thatof 4G, while other 5G cells may employ frequency spectrum in themillimeter wave band. Cells in the millimeter wave band will have arelatively small coverage area but will offer much higher throughputthan 4G.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood withreference to the following drawings. The components in the drawings arenot necessarily to scale, with emphasis instead being placed uponclearly illustrating the principles of the disclosure. Moreover, in thedrawings, like reference numerals designate corresponding partsthroughout the several views.

FIG. 1A is a drawing of an example of a communication network thatdeployed and managed according to various embodiments of the presentdisclosure.

FIG. 1B is an example of a radio-based private network used on anorganizational campus with a plurality of buildings and deployed inaccordance with various embodiments of the present disclosure.

FIG. 2A illustrates an example of a networked environment including acloud provider network and further including various provider substrateextensions of the cloud provider network, which may be used in variouslocations within the communication network of FIG. 1A, according to someembodiments of the present disclosure.

FIG. 2B depicts an example of cellularization and geographicdistribution of the communication network of FIG. 1A.

FIG. 3A illustrates an example of the networked environment of FIG. 2Aincluding geographically dispersed provider substrate extensionsaccording to some embodiments of the present disclosure.

FIG. 3B depicts a state diagram for creation and management of aradio-based private network.

FIG. 4 is a schematic block diagram of the networked environment of FIG.2A according to various embodiments of the present disclosure.

FIGS. 5 and 6 are flowcharts illustrating examples of functionalityimplemented as portions of a radio-based private network managementservice and a radio unit management service executed in a computingenvironment in the networked environment of FIG. 4 according to variousembodiments of the present disclosure.

FIG. 7 is a schematic block diagram that provides one exampleillustration of a computing environment employed in the networkedenvironment of FIG. 4 according to various embodiments of the presentdisclosure.

DETAILED DESCRIPTION

The present disclosure relates to interfaces that facilitate theautomated deployment and modification of radio-based private networks,such as 4G and 5G radio access networks, or portions of such radio-basednetworks, and associated core networks using cloud provider networkinfrastructure. Such interfaces may include user interfaces and/orapplication programming interfaces (APIs). Previous deployments ofradio-based networks have relied upon manual deployment andconfiguration at each step of the process. This proved to be extremelytime consuming and expensive. Further, in previous generations, softwarewas inherently tied to vendor-specific hardware, thereby preventingcustomers from deploying alternative software. By contrast, with 5G,hardware is decoupled from the software stack, which allows moreflexibility, and allows components of the radio-based network to beexecuted on cloud provider infrastructure. Using a cloud delivery modelfor a radio-based network, such as a 5G network, can facilitate handlingnetwork traffic from hundreds up to billions of connected devices andcompute-intensive applications, while delivering faster speeds, lowerlatency, and more capacity than other types of networks.

Historically, enterprises have had to choose between performance andprice when evaluating their enterprise connectivity solutions. Cellularnetworks may offer high performance, great indoor and outdoor coverage,and advanced Quality of Service (QoS) connectivity features, but privatecellular networks can be expensive and complex to manage. While Ethernetand Wi-Fi require less upfront investment and are easier to manage,enterprises often find that they can be less reliable, require a lot ofwork to get the best coverage, and do not offer QoS features such asguaranteed bit rate, latency, and reliability.

The disclosed private radio-based network service can give enterprisesthe best of both worlds—the performance, coverage, and QoS of aTelco-grade cellular network, with ease and cost of deployment andoperation associated with Wi-Fi. The disclosed service can providesuitable hardware in different form factors that enterprises can deployto their sites, and comes integrated with software that runs the entirenetwork, from small cell sites to the internet break-outs. Enterprisescan freely deploy various 5G devices and sensors across theenterprise—factory floors, warehouses, lobbies, and communicationscenters—and manage these devices, enroll users, and assign QoS from amanagement console. With the disclosed technology, customers can assignconstant bit rate throughput to all their devices (such as cameras,sensors, or IoT devices), reliable low latency connection to devicesrunning on factory floors, and broadband connectivity to all handhelddevices. The disclosed service can manage all the software needed todeliver connectivity that meets the specified constraints andrequirements. This enables an entirely new set of applications that havestrict QoS or high IoT device density requirements that traditionallyhave not been able to run on Wi-Fi networks.

The disclosed service supports multiple deployment scenarios. In a cloudonly deployment, the service can provide small radio cells that anenterprise customer can place on site, while the network functions andother network software are run in the closest (or one of severalclosest) cloud provider availability zones or edge locations. Forenterprises that want an on-premise deployment, the disclosed serviceprovides cloud-provider hardware such as the substrate extensionsdescribed herein. In this mode, the network and applications remain onpremises for the enterprise, enabling the enterprise to securely storeand process data that needs to remain local (e.g., for regulatorycompliance, security concerns, etc.). Further, the disclosed service canallow any compute and storage that is not being used for running theradio-based network to be used to run any local workloads via the sameAPIs that customers can use to run workloads in traditional cloudprovider regions. Beneficially, because of this enterprises do not haveto worry about being over-scaled and wasting capacity, because theservice will enable any excess capacity to be used for local processingand will provision new hardware and software as the needs of the networkchange. Further, the disclosed service can provide applicationdevelopment APIs that expose and manage 5G capabilities like QoS,enabling customers to build applications that can fully utilize thelatency and bandwidth capabilities of their network without having tounderstand the details of the network.

Additionally, the disclosed service can provide a private zone to runlocal applications within a cloud provider network. This private zonecan be connected to and effectively part of a broader regional zone, andallows the customer to manage the private zone using the same APIs andtools as used in the cloud provider network. Like an availability zone,the private zone can be assigned a virtual private network subnet. AnAPI can be used to create and assign subnets to all zones that thecustomer wishes to use, including the private zone and existing otherzones. A management console may offer a simplified process for creatinga private zone. Virtual machine instances and containers can be launchedin the private zone just as in regional zones. Customer can configure anetwork gateway to define routes, assign IP addresses, set up networkaddress translation (NAT), and so forth. Automatic scaling can be usedto scale the capacity of virtual machine instances or containers asneeded in the private zone. The same management and authentication APIsof the cloud provider network can be used within the private zone. Insome cases, since cloud services available in the regional zone can beaccessed remotely from private zones over a secure connection, thesecloud services can be accessed without having to upgrade or modify thelocal deployment.

Various embodiments of the present disclosure introduce approaches thatallow customers to order and deploy a radio-based private network and anassociated core network in an automated way. The customers may includeenterprises and organizations that wish to set up a radio-based networkfor internal uses (e.g., a private 5G network). Through various userinterfaces or APIs, a customer may specify its network plan orrequirements (for example, physical site layout and device/applicationtypes and quantities), and the various components necessary to implementa radio-based private network for the customer may be automaticallydetermined and provisioned. Hardware, such as antennas, radios, andcomputer servers, may be preconfigured for the customer's radio-basedprivate network and shipped to the customer. The process of installingthe preconfigured hardware is largely plug-and-play, and the radio-basedprivate network can be activated through a user interface or API. Inaddition to deploying a radio-based private network, such as all or aportion of a new radio access network, various embodiments of thepresent disclosure may facilitate modification and management of theradio-based private network, including the deployment of preconfiguredequipment for additional cells, and the assignment of QoS constraintsfor particular devices or applications on their radio-based privatenetwork.

Various embodiments of the present disclosure may also bring the conceptof elasticity and utility computing from the cloud computing model toradio-based private networks and associated core networks. For example,the disclosed techniques can run core and radio access network functionsand associated control plane management functions on cloud providerinfrastructure, creating a cloud native core network and/or a cloudnative radio access network (RAN). Such core and RAN network functionscan be based on the 3rd Generation Partnership Project (3GPP)specifications in some implementations. By providing a cloud-nativeradio-based network, a customer may dynamically scale its radio-basedprivate network based on utilization, latency requirements, and/or otherfactors. In some cases, the hardware sent to the customer includesufficient capacity to run both programs for operation and management ofthe radio-based network as well as other workloads of the customer(e.g., their applications), such that any capacity not used for theradio-based network can be accessible to run workloads under a utilitycomputing model. Beneficially, the customer's radio-based network canscale up into this excess capacity as needed, for example, allowing thehardware usage requirements of the radio-based network to increase evenbefore new physical hardware is provisioned to the customer. Customersmay also configure thresholds to receive alerts relating to radio-basednetwork usage and excess capacity usage of their provisionedinfrastructure, in order to more effectively manage provisioning of newinfrastructure or deprovisioning of existing infrastructure based ontheir dynamic networking and workload requirements.

As one skilled in the art will appreciate in light of this disclosure,certain embodiments may be capable of achieving certain advantages,including some or all of the following: (1) improving the userexperience by allowing organizations to deploy their own radio-basedprivate networks in a largely automated, plug-and-play way; (2)improving flexibility in computer systems by allowing computing hardwarepreviously dedicated to network functions in radio-based networks andassociated core networks to be repurposed for other applications; (3)improving flexibility in computer systems by allowing computing hardwarepreviously dedicated to a first radio-based private network to berepurposed automatically for a second radio-based private network (or tobe repurposed between RAN and core network functions of the sameradio-based network on an as-needed basis); (4) improving the userexperience in deploying a radio-based private network by preconfiguringantennas, radios, and other hardware, thereby providing a plug-and-playinstallation experience; (5) improving the performance of radio-basedprivate networks by optimizing deployment of cells and spectrumutilization; (6) improving the performance and management of radio-basednetworks by monitoring performance metrics and adding, removing, andreconfiguring cells as needed to maintain acceptable performance; (7)improving the scalability and overall performance of a radio-basedprivate network by transferring network functions previously provided byproprietary hardware to virtual machine instances operated by a cloudcomputing provider with elasticity under a utility computing model; (8)reducing latency in a radio-based private network by transferringnetwork functions to virtual machine instances executed on computingdevices of a cloud service provider at a cell site; (9) improvingsecurity of the radio-based private network by configuring networkfunction workloads to remain on a customer's premises; and so forth.

Among the benefits of the present disclosure is the ability to deployand chain network functions together to deliver an end-to-end servicethat meets specified constraints and requirements. According to thepresent disclosure, network functions organized into microservices worktogether to provide end-to-end connectivity. One set of networkfunctions are part of a radio network, running in cell towers andperforming wireless signal to IP conversion. Other network functions runin large data centers performing subscriber related business logic androuting IP traffic to the internet and back. For applications to use thenew capabilities of 5G such as low latency communication and reservedbandwidth, both of these types of network functions need to worktogether to appropriately schedule and reserve wireless spectrum, andperform real time compute and data processing. The presently disclosedtechniques provide edge location hardware (as described further below)integrated with network functions that run across the entire network,from cell sites to Internet break-outs, and orchestrates the networkfunctions to meet required Quality of Service (QoS) constraints. Thisenables an entirely new set of applications that have strict QoSrequirements, from factory-based Internet of Things (IoT), to augmentedreality (AR), to virtual reality (VR), to game streaming, to autonomousnavigation support for connected vehicles, that previously could not runon a mobile network.

The described “elastic 5G” service provides and manages all thehardware, software, and network functions required to build a network.In some embodiments, the network functions may be developed and managedby the cloud service provider; however, the described control plane canmanage network functions across a range of providers so that customerscan use a single set of APIs to call and manage their choice of networkfunctions on cloud infrastructure. The elastic 5G service beneficiallyautomates the creation of an end-to-end 5G network, from hardware tonetwork functions thus reducing the time to deploy and the operationalcost of operating the network. By providing APIs that expose networkcapabilities, the disclosed elastic 5G service enables applications tosimply specify the desired QoS as constraints and then deploys andchains the network functions together to deliver an end-to-end servicethat meets the specified requirements, thus making it possible to easilybuild new applications.

The present disclosure describes embodiments relating to the creationand management of a cloud native 5G core and/or a cloud native 5G RAN,and associated control plane components. Cloud native refers to anapproach to building and running applications that exploits theadvantages of the cloud computing delivery model such as dynamicscalability, distributed computing, and high availability (includinggeographic distribution, redundancy, and failover). Cloud native refersto how these applications are created and deployed to be suitable fordeployment in a public cloud. While cloud native applications can be(and often are) run in the public cloud, they also can be run in anon-premises data center. Some cloud native applications can becontainerized, for example, having different parts, functions, orsubunits of the application packaged in their own containers, which canbe dynamically orchestrated so that each part is actively scheduled andmanaged to optimize resource utilization. These containerizedapplications can be architected using a microservices architecture toincrease the overall agility and maintainability of the applications.

In a microservices architecture, an application is arranged as acollection of smaller subunits (“microservices”) that can be deployedand scaled independently from one another, and which can communicatewith one another over a network. These microservices are typicallyfine-grained, in that they have specific technical and functionalgranularity, and often implement lightweight communications protocols.The microservices of an application can perform different functions fromone another, can be independently deployable, and may use differentprogramming languages, databases, and hardware/software environment fromone another. Decomposing an application into smaller servicesbeneficially improves modularity of the application, enables replacementof individual microservices as needed, and parallelizes development byenabling teams to develop, deploy, and maintain their microservicesindependently from one another. A microservice may be deployed using avirtual machine, container, or serverless function, in some examples.The disclosed core and RAN software may follow a microservicesarchitecture such that the described radio-based networks are composedof independent subunits that can be deployed and scaled on demand.

Turning now to FIG. 1A, shown is an example of a communication network100 that deployed and managed according to various embodiments of thepresent disclosure. The communication network 100 includes a radio-basedprivate network 103, which may correspond to a cellular network such asa fourth-generation (4G) Long-Term Evolution (LTE) network, afifth-generation (5G) network, a 4G-5G hybrid core with both 4G and 5GRANs, or another network that provides wireless network access. Theradio-based private network 103 may be operated by a cloud serviceprovider for an enterprise, a non-profit, a school system, agovernmental entity or other organization. Although referred to as aprivate network, the radio-based private network 103 may use privatenetwork addresses or public network addresses in various embodiments.

Various deployments of radio-based private network 103 can include oneor more of a core network and a RAN network, as well as a control planefor running the core and/or RAN network on cloud providerinfrastructure. As described above, these components can be developed ina cloud native fashion, for example using a microservices architecture,such that centralized control and distributed processing is used toscale traffic and transactions efficiently. These components may bebased on the 3GPP specifications by following an applicationarchitecture in which control plane and user plane processing isseparated (CUPS Architecture).

The radio-based private network 103 provides wireless network access toa plurality of wireless devices 106, which may be mobile devices orfixed location devices. In various examples, the wireless devices 106may include smartphones, connected vehicles, IoT devices, sensors,machinery (such as in a manufacturing facility), hotspots, and otherdevices. The wireless devices 106 are sometimes referred to as userequipment (UE) or customer premises equipment (CPE).

The radio-based private network 103 can include a radio access network(RAN) that provides the wireless network access to the plurality ofwireless devices 106 through a plurality of cells 109. Each of the cells109 may be equipped with one or more antennas and one or more radiounits that send and receive wireless data signals to and from thewireless devices 106. The antennas may be configured for one or morefrequency bands, and the radio units may also be frequency agile orfrequency adjustable. The antennas may be associated with a certain gainor beamwidth in order to focus a signal in a particular direction orazimuthal range, potentially allowing reuse of frequencies in adifferent direction. Further, the antennas may be horizontally,vertically, or circularly polarized. In some examples, a radio unit mayutilize multiple-input, multiple-output (MIMO) technology to send andreceive signals. As such, the RAN implements a radio access technologyto enable radio connection with wireless devices 106, and providesconnection with the radio-based private network's core network.Components of the RAN include a base station and antennas that cover agiven physical area, as well as required core network items for managingconnections to the RAN.

Data traffic is often routed through a fiber transport networkconsisting of multiple hops of layer 3 routers (e.g., at aggregationsites) to the core network. The core network is typically housed in oneor more data centers. The core network typically aggregates data trafficfrom end devices, authenticates subscribers and devices, appliespersonalized policies, and manages the mobility of the devices beforerouting the traffic to operator services or the Internet. A 5G Core forexample can be decomposed into a number of microservice elements withcontrol and user plane separation. Rather than physical networkelements, a 5G Core can comprise virtualized, software-based networkfunctions (deployed for example as microservices) and can therefore beinstantiated within Multi-access Edge Computing (MEC) cloudinfrastructures. The network functions of the core network can include aUser Plane Function (UPF), Access and Mobility Management Function(AMF), and Session Management Function (SMF), described in more detailbelow. For data traffic destined for locations outside of thecommunication network 100, network functions typically include afirewall through which traffic can enter or leave the communicationnetwork 100 to external networks such as the Internet or a cloudprovider network. Note that in some embodiments, the communicationnetwork 100 can include facilities to permit traffic to enter or leavefrom sites further downstream from the core network (e.g., at anaggregation site or radio-based private network 103).

The UPF provides an interconnect point between the mobile infrastructureand the Data Network (DN), i.e., encapsulation and decapsulation ofGeneral Packet Radio Service (GPRS) tunneling protocol for the userplane (GTP-U). The UPF can also provide a session anchor point forproviding mobility within the RAN, including sending one or more endmarker packets to the RAN base stations. The UPF can also handle packetrouting and forwarding, including directing flows to specific datanetworks based on traffic matching filters. Another feature of the UPFincludes per-flow or per-application QoS handling, including transportlevel packet marking for uplink (UL) and downlink (DL), and ratelimiting. The UPF can be implemented as a cloud native network functionusing modern microservices methodologies, for example being deployablewithin a serverless framework (which abstracts away the underlyinginfrastructure that code runs on via a managed service).

The AMF can receive the connection and session information from thewireless devices 106 or the RAN and can handle connection and mobilitymanagement tasks. For example, the AMF can manage handovers between basestations in the RAN. In some examples the AMF can be considered as theaccess point to the 5G core, by terminating certain RAN control planeand wireless device 106 traffic. The AMF can also implement cipheringand integrity protection algorithms.

The SMF can handle session establishment or modification, for example bycreating, updating, and removing Protocol Data Unit (PDU) sessions andmanaging session context within the UPF. The SMF can also implementDynamic Host Configuration Protocol (DHCP) and IP Address Management(IPAM). The SMF can be implemented as a cloud native network functionusing modern microservices methodologies.

Various network functions to implement the radio-based private network103 may be deployed in distributed computing devices 112, which maycorrespond to general-purpose computing devices configured to performthe network functions. For example, the distributed computing devices112 may execute one or more virtual machine instances that areconfigured in turn to execute one or more services that perform thenetwork functions. In one embodiment, the distributed computing devices112 are ruggedized machines that are deployed at each cell site.

By contrast, one or more centralized computing devices 115 may performvarious network functions at a central site operated by the customer.For example, the centralized computing devices 115 may be centrallylocated on premises of the customer in a conditioned server room. Thecentralized computing devices 115 may execute one or more virtualmachine instances that are configured in turn to execute one or moreservices that perform the network functions.

In one or more embodiments, network traffic from the radio-based privatenetwork 103 is backhauled to one or more computing devices on a corenetwork 118 that may be located at one or more data centers situatedremotely from the customer's site. The core network 118 may also performvarious network functions, including routing network traffic to and fromthe network 121, which may correspond to the Internet and/or otherexternal public or private networks. The core network 118 may performfunctionality related to the management of the communication network 100(e.g., billing, mobility management, etc.) and transport functionalityto relay traffic between the communication network 100 and othernetworks.

Moving on to FIG. 1B, shown is an example of a radio-based privatenetwork 150 used on an organizational campus (such as the premises of anenterprise such as a business, school, or other organization) with aplurality of buildings 153 and deployed in accordance with variousembodiments of the present disclosure. Although FIG. 1B depicts anexample with multiple buildings, it will be appreciated that thedisclosed techniques can similarly be applied to any layout of a site,which may include one or more buildings and/or one or more outdoorspaces (such as stadiums or other outdoor venues).

The radio-based private network 150 in this non-limiting exampleincludes four cells 156 a, 156 b, 156 c, and 156 d to fully cover theorganizational campus. The cells 156 may overlap somewhat in order toprovide exhaustive coverage within each of the buildings 153. Theadjacent or overlapping cells 156 are configured to operate withnon-interfering frequencies. For example, cell 156 a may use FrequencyA, cell 156 b may use Frequency B, and cell 156 c may use Frequency C,which are all distinct frequencies as the coverage of the respectivecells 156 a, 156 b, and 156 c overlap. However, cell 156 d may use, forexample, Frequency A or B as the coverage of cell 156 d does not overlapcell 156 a or 156 b.

It is noted that depending on usage or other network metrics, cells 156may be added or removed from the radio-based private network 150. Insome cases, signal strength to cells 156 may be increased to reduce thenumber of cells 156, or lowered to increase the number of cells 156while allowing for spectrum reuse among the cells 156. Additionally,computing capacity may be added within the geographic area of theorganizational campus or within a cloud provider network in order todecrease latency, maintain security, and increase reliability, for theradio-based private network 150 as desired. In some cases, computingcapacity for software that implements the radio-based private network150 may be provisioned mostly or wholly in a cloud provider network andnot on a customer's premises, such as in a regional data center of acloud service provider. This software may implement various networkfunctions such as the UPF, AMF, SMF, and so forth, that may correspondto the core network functions, central unit network functions, anddistributed unit network functions. Some network functions, such asdistributed unit network functions, may remain at the cell site.

FIG. 2A illustrates an example of a networked environment 200 includinga cloud provider network 203 and further including various providersubstrate extensions of the cloud provider network, which may be used incombination with on-premise customer deployments within thecommunication network 100 of FIG. 1 , according to some embodiments. Acloud provider network 203 (sometimes referred to simply as a “cloud”)refers to a pool of network-accessible computing resources (such ascompute, storage, and networking resources, applications, and services),which may be virtualized or bare-metal. The cloud can provideconvenient, on-demand network access to a shared pool of configurablecomputing resources that can be programmatically provisioned andreleased in response to customer commands. These resources can bedynamically provisioned and reconfigured to adjust to variable load.Cloud computing can thus be considered as both the applicationsdelivered as services over a publicly accessible network (e.g., theInternet, a cellular communication network) and the hardware andsoftware in cloud provider data centers that provide those services.

The cloud provider network 203 can provide on-demand, scalable computingplatforms to users through a network, for example, allowing users tohave at their disposal scalable “virtual computing devices” via theiruse of the compute servers (which provide compute instances via theusage of one or both of central processing units (CPUs) and graphicsprocessing units (GPUs), optionally with local storage) and block storeservers (which provide virtualized persistent block storage fordesignated compute instances). These virtual computing devices haveattributes of a personal computing device including hardware (varioustypes of processors, local memory, random access memory (RAM),hard-disk, and/or solid-state drive (SSD) storage), a choice ofoperating systems, networking capabilities, and pre-loaded applicationsoftware. Each virtual computing device may also virtualize its consoleinput and output (e.g., keyboard, display, and mouse). Thisvirtualization allows users to connect to their virtual computing deviceusing a computer application such as a browser, API, softwaredevelopment kit (SDK), or the like, in order to configure and use theirvirtual computing device just as they would a personal computing device.Unlike personal computing devices, which possess a fixed quantity ofhardware resources available to the user, the hardware associated withthe virtual computing devices can be scaled up or down depending uponthe resources the user requires.

As indicated above, users can connect to virtualized computing devicesand other cloud provider network 203 resources and services, andconfigure and manage telecommunications networks such as 5G networks,using various interfaces 206 (e.g., APIs) via intermediate network(s)212. An API refers to an interface and/or communication protocol betweena client device 215 and a server, such that if the client makes arequest in a predefined format, the client should receive a response ina specific format or cause a defined action to be initiated. In thecloud provider network context, APIs provide a gateway for customers toaccess cloud infrastructure by allowing customers to obtain data from orcause actions within the cloud provider network, enabling thedevelopment of applications that interact with resources and serviceshosted in the cloud provider network. APIs can also enable differentservices of the cloud provider network to exchange data with oneanother. Users can choose to deploy their virtual computing systems toprovide network-based services for their own use and/or for use by theircustomers or clients.

The cloud provider network 203 can include a physical network (e.g.,sheet metal boxes, cables, rack hardware) referred to as the substrate.The substrate can be considered as a network fabric containing thephysical hardware that runs the services of the provider network. Thesubstrate may be isolated from the rest of the cloud provider network203, for example it may not be possible to route from a substratenetwork address to an address in a production network that runs servicesof the cloud provider, or to a customer network that hosts customerresources.

The cloud provider network 203 can also include an overlay network ofvirtualized computing resources that run on the substrate. In at leastsome embodiments, hypervisors or other devices or processes on thenetwork substrate may use encapsulation protocol technology toencapsulate and route network packets (e.g., client IP packets) over thenetwork substrate between client resource instances on different hostswithin the provider network. The encapsulation protocol technology maybe used on the network substrate to route encapsulated packets (alsoreferred to as network substrate packets) between endpoints on thenetwork substrate via overlay network paths or routes. The encapsulationprotocol technology may be viewed as providing a virtual networktopology overlaid on the network substrate. As such, network packets canbe routed along a substrate network according to constructs in theoverlay network (e.g., virtual networks that may be referred to asvirtual private clouds (VPCs), port/protocol firewall configurationsthat may be referred to as security groups). A mapping service (notshown) can coordinate the routing of these network packets. The mappingservice can be a regional distributed look up service that maps thecombination of overlay internet protocol (IP) and network identifier tosubstrate IP so that the distributed substrate computing devices canlook up where to send packets.

To illustrate, each physical host device (e.g., a compute server, ablock store server, an object store server, a control server) can havean IP address in the substrate network. Hardware virtualizationtechnology can enable multiple operating systems to run concurrently ona host computer, for example as virtual machines (VMs) on a computeserver. A hypervisor, or virtual machine monitor (VMM), on a hostallocates the host's hardware resources amongst various VMs on the hostand monitors the execution of VMs. Each VM may be provided with one ormore IP addresses in an overlay network, and the VMM on a host may beaware of the IP addresses of the VMs on the host. The VMMs (and/or otherdevices or processes on the network substrate) may use encapsulationprotocol technology to encapsulate and route network packets (e.g.,client IP packets) over the network substrate between virtualizedresources on different hosts within the cloud provider network 203. Theencapsulation protocol technology may be used on the network substrateto route encapsulated packets between endpoints on the network substratevia overlay network paths or routes. The encapsulation protocoltechnology may be viewed as providing a virtual network topologyoverlaid on the network substrate. The encapsulation protocol technologymay include the mapping service that maintains a mapping directory thatmaps IP overlay addresses (e.g., IP addresses visible to customers) tosubstrate IP addresses (IP addresses not visible to customers), whichcan be accessed by various processes on the cloud provider network 203for routing packets between endpoints.

As illustrated, the traffic and operations of the cloud provider networksubstrate may broadly be subdivided into two categories in variousembodiments: control plane traffic carried over a logical control plane218 and data plane operations carried over a logical data plane 221.While the data plane 221 represents the movement of user data throughthe distributed computing system, the control plane 218 represents themovement of control signals through the distributed computing system.The control plane 218 generally includes one or more control planecomponents or services distributed across and implemented by one or morecontrol servers. Control plane traffic generally includes administrativeoperations, such as establishing isolated virtual networks for variouscustomers, monitoring resource usage and health, identifying aparticular host or server at which a requested compute instance is to belaunched, provisioning additional hardware as needed, and so on. Thedata plane 221 includes customer resources that are implemented on thecloud provider network (e.g., computing instances, containers, blockstorage volumes, databases, file storage). Data plane traffic generallyincludes non-administrative operations such as transferring data to andfrom the customer resources.

The control plane components are typically implemented on a separate setof servers from the data plane servers, and control plane traffic anddata plane traffic may be sent over separate/distinct networks. In someembodiments, control plane traffic and data plane traffic can besupported by different protocols. In some embodiments, messages (e.g.,packets) sent over the cloud provider network 203 include a flag toindicate whether the traffic is control plane traffic or data planetraffic. In some embodiments, the payload of traffic may be inspected todetermine its type (e.g., whether control or data plane). Othertechniques for distinguishing traffic types are possible.

As illustrated, the data plane 221 can include one or more computeservers, which may be bare metal (e.g., single tenant) or may bevirtualized by a hypervisor to run multiple VMs (sometimes referred toas “instances”) or microVMs for one or more customers. These computeservers can support a virtualized computing service (or “hardwarevirtualization service”) of the cloud provider network. The virtualizedcomputing service may be part of the control plane 218, allowingcustomers to issue commands via an interface 206 (e.g., an API) tolaunch and manage compute instances (e.g., VMs, containers) for theirapplications. The virtualized computing service may offer virtualcompute instances with varying computational and/or memory resources. Inone embodiment, each of the virtual compute instances may correspond toone of several instance types. An instance type may be characterized byits hardware type, computational resources (e.g., number, type, andconfiguration of CPUs or CPU cores), memory resources (e.g., capacity,type, and configuration of local memory), storage resources (e.g.,capacity, type, and configuration of locally accessible storage),network resources (e.g., characteristics of its network interface and/ornetwork capabilities), and/or other suitable descriptivecharacteristics. Using instance type selection functionality, aninstance type may be selected for a customer, e.g., based (at least inpart) on input from the customer. For example, a customer may choose aninstance type from a predefined set of instance types. As anotherexample, a customer may specify the desired resources of an instancetype and/or requirements of a workload that the instance will run, andthe instance type selection functionality may select an instance typebased on such a specification.

The data plane 221 can also include one or more block store servers,which can include persistent storage for storing volumes of customerdata as well as software for managing these volumes. These block storeservers can support a managed block storage service of the cloudprovider network. The managed block storage service may be part of thecontrol plane 218, allowing customers to issue commands via theinterface 206 (e.g., an API) to create and manage volumes for theirapplications running on compute instances. The block store serversinclude one or more servers on which data is stored as blocks. A blockis a sequence of bytes or bits, usually containing some whole number ofrecords, having a maximum length of the block size. Blocked data isnormally stored in a data buffer and read or written a whole block at atime. In general, a volume can correspond to a logical collection ofdata, such as a set of data maintained on behalf of a user. Uservolumes, which can be treated as an individual hard drive ranging forexample from 1 GB to 1 terabyte (TB) or more in size, are made of one ormore blocks stored on the block store servers. Although treated as anindividual hard drive, it will be appreciated that a volume may bestored as one or more virtualized devices implemented on one or moreunderlying physical host devices. Volumes may be partitioned a smallnumber of times (e.g., up to 16) with each partition hosted by adifferent host. The data of the volume may be replicated betweenmultiple devices within the cloud provider network, in order to providemultiple replicas of the volume (where such replicas may collectivelyrepresent the volume on the computing system). Replicas of a volume in adistributed computing system can beneficially provide for automaticfailover and recovery, for example by allowing the user to access eithera primary replica of a volume or a secondary replica of the volume thatis synchronized to the primary replica at a block level, such that afailure of either the primary or secondary replica does not inhibitaccess to the information of the volume. The role of the primary replicacan be to facilitate reads and writes (sometimes referred to as “inputoutput operations,” or simply “I/O operations”) at the volume, and topropagate any writes to the secondary (preferably synchronously in theI/O path, although asynchronous replication can also be used). Thesecondary replica can be updated synchronously with the primary replicaand provide for seamless transition during failover operations, wherebythe secondary replica assumes the role of the primary replica, andeither the former primary is designated as the secondary or a newreplacement secondary replica is provisioned. Although certain examplesherein discuss a primary replica and a secondary replica, it will beappreciated that a logical volume can include multiple secondaryreplicas. A compute instance can virtualize its I/O to a volume by wayof a client. The client represents instructions that enable a computeinstance to connect to, and perform I/O operations at, a remote datavolume (e.g., a data volume stored on a physically separate computingdevice accessed over a network). The client may be implemented on anoffload card of a server that includes the processing units (e.g., CPUsor GPUs) of the compute instance.

The data plane 221 can also include one or more object store servers,which represent another type of storage within the cloud providernetwork. The object storage servers include one or more servers on whichdata is stored as objects within resources referred to as buckets andcan be used to support a managed object storage service of the cloudprovider network. Each object typically includes the data being stored,a variable amount of metadata that enables various capabilities for theobject storage servers with respect to analyzing a stored object, and aglobally unique identifier or key that can be used to retrieve theobject. Each bucket is associated with a given user account. Customerscan store as many objects as desired within their buckets, can write,read, and delete objects in their buckets, and can control access totheir buckets and the objects contained therein. Further, in embodimentshaving a number of different object storage servers distributed acrossdifferent ones of the regions described above, users can choose theregion (or regions) where a bucket is stored, for example to optimizefor latency. Customers may use buckets to store objects of a variety oftypes, including machine images that can be used to launch VMs, andsnapshots that represent a point-in-time view of the data of a volume.

A provider substrate extension 224 (“PSE”) provides resources andservices of the cloud provider network 203 within a separate network,such as a telecommunications network, thereby extending functionality ofthe cloud provider network 203 to new locations (e.g., for reasonsrelated to latency in communications with customer devices, legalcompliance, security, etc.). In some implementations, a PSE 224 can beconfigured to provide capacity for cloud-based workloads to run withinthe telecommunications network. In some implementations, a PSE 224 canbe configured to provide the core and/or RAN functions of thetelecommunications network, and may be configured with additionalhardware (e.g., radio access hardware). Some implementations may beconfigured to allow for both, for example by allowing capacity unused bycore and/or RAN functions to be used for running cloud-based workloads.

As indicated, such provider substrate extensions 224 can include cloudprovider network-managed provider substrate extensions 227 (e.g., formedby servers located in a cloud provider-managed facility separate fromthose associated with the cloud provider network 203), communicationsservice provider substrate extensions 230 (e.g., formed by serversassociated with communications service provider facilities),customer-managed provider substrate extensions 233 (e.g., formed byservers located on-premise in a customer or partner facility), amongother possible types of substrate extensions.

As illustrated in the example provider substrate extension 224, aprovider substrate extension 224 can similarly include a logicalseparation between a control plane 236 and a data plane 239,respectively extending the control plane 218 and data plane 221 of thecloud provider network 203. The provider substrate extension 224 may bepre-configured, e.g., by the cloud provider network operator, with anappropriate combination of hardware with software and/or firmwareelements to support various types of computing-related resources, and todo so in a manner that mirrors the experience of using the cloudprovider network. For example, one or more provider substrate extensionlocation servers can be provisioned by the cloud provider for deploymentwithin a provider substrate extension 224. As described above, the cloudprovider network 203 may offer a set of predefined instance types, eachhaving varying types and quantities of underlying hardware resources.Each instance type may also be offered in various sizes. In order toenable customers to continue using the same instance types and sizes ina provider substrate extension 224 as they do in the region, the serverscan be heterogeneous servers. A heterogeneous server can concurrentlysupport multiple instance sizes of the same type and may be alsoreconfigured to host whatever instance types are supported by itsunderlying hardware resources. The reconfiguration of the heterogeneousserver can occur on-the-fly using the available capacity of the servers,that is, while other VMs are still running and consuming other capacityof the provider substrate extension location servers. This can improveutilization of computing resources within the edge location by allowingfor better packing of running instances on servers, and also provides aseamless experience regarding instance usage across the cloud providernetwork 203 and the cloud provider network-managed provider substrateextension 227.

The provider substrate extension servers can host one or more computeinstances. Compute instances can be VMs, or containers that package upcode and all its dependencies so an application can run quickly andreliably across computing environments (e.g., including VMs andmicroVMs). In addition, the servers may host one or more data volumes,if desired by the customer. In the region of a cloud provider network203, such volumes may be hosted on dedicated block store servers.However, due to the possibility of having a significantly smallercapacity at a provider substrate extension 224 than in the region, anoptimal utilization experience may not be provided if the providersubstrate extension 224 includes such dedicated block store servers.Accordingly, a block storage service may be virtualized in the providersubstrate extension 224, such that one of the VMs runs the block storesoftware and stores the data of a volume. Similar to the operation of ablock storage service in the region of a cloud provider network 203, thevolumes within a provider substrate extension 224 may be replicated fordurability and availability. The volumes may be provisioned within theirown isolated virtual network within the provider substrate extension224. The compute instances and any volumes collectively make up a dataplane 239 extension of the provider network data plane 221 within theprovider substrate extension 224.

The servers within a provider substrate extension 224 may, in someimplementations, host certain local control plane components, forexample, components that enable the provider substrate extension 224 tocontinue functioning if there is a break in the connection back to thecloud provider network 203. Examples of these components include amigration manager that can move compute instances between providersubstrate extension servers if needed to maintain availability, and akey value data store that indicates where volume replicas are located.However, generally the control plane 236 functionality for a providersubstrate extension will remain in the cloud provider network 203 inorder to allow customers to use as much resource capacity of theprovider substrate extension as possible.

The migration manager may have a centralized coordination component thatruns in the region, as well as local controllers that run on the PSEservers (and servers in the cloud provider's data centers). Thecentralized coordination component can identify target edge locationsand/or target hosts when a migration is triggered, while the localcontrollers can coordinate the transfer of data between the source andtarget hosts. The described movement of the resources between hosts indifferent locations may take one of several forms of migration.Migration refers to moving virtual machine instances (and/or otherresources) between hosts in a cloud computing network, or between hostsoutside of the cloud computing network and hosts within the cloud. Thereare different types of migration including live migration and rebootmigration. During a reboot migration, the customer experiences an outageand an effective power cycle of their virtual machine instance. Forexample, a control plane service can coordinate a reboot migrationworkflow that involves tearing down the current domain on the originalhost and subsequently creating a new domain for the virtual machineinstance on the new host. The instance is rebooted by being shut down onthe original host and booted up again on the new host.

Live migration refers to the process of moving a running virtual machineor application between different physical machines without significantlydisrupting the availability of the virtual machine (e.g., the down timeof the virtual machine is not noticeable by the end user). When thecontrol plane executes a live migration workflow it can create a new“inactive” domain associated with the instance, while the originaldomain for the instance continues to run as the “active” domain. Memory(including any in-memory state of running applications), storage, andnetwork connectivity of the virtual machine are transferred from theoriginal host with the active domain to the destination host with theinactive domain. The virtual machine may be briefly paused to preventstate changes while transferring memory contents to the destinationhost. The control plane can transition the inactive domain to become theactive domain and demote the original active domain to become theinactive domain (sometimes referred to as a “flip”), after which theinactive domain can be discarded.

Techniques for various types of migration involve managing the criticalphase—the time when the virtual machine instance is unavailable to thecustomer—which should be kept as short as possible. In the presentlydisclosed migration techniques this can be especially challenging, asresources are being moved between hosts in geographically separatelocations which may be connected over one or more intermediate networks.For live migration, the disclosed techniques can dynamically determinean amount of memory state data to pre-copy (e.g., while the instance isstill running on the source host) and to post-copy (e.g., after theinstance begins running on the destination host), based for example onlatency between the locations, network bandwidth/usage patterns, and/oron which memory pages are used most frequently by the instance. Further,a particular time at which the memory state data is transferred can bedynamically determined based on conditions of the network between thelocations. This analysis may be performed by a migration managementcomponent in the region, or by a migration management component runninglocally in the source edge location. If the instance has access tovirtualized storage, both the source domain and target domain can besimultaneously attached to the storage to enable uninterrupted access toits data during the migration and in the case that rollback to thesource domain is required.

Server software running at a provider substrate extension 224 may bedesigned by the cloud provider to run on the cloud provider substratenetwork, and this software may be enabled to run unmodified in aprovider substrate extension 224 by using local network manager(s) 242to create a private replica of the substrate network within the edgelocation (a “shadow substrate”). The local network manager(s) 242 canrun on provider substrate extension 224 servers and bridge the shadowsubstrate with the provider substrate extension 224 network, forexample, by acting as a virtual private network (VPN) endpoint orendpoints between the provider substrate extension 224 and the proxies245, 248 in the cloud provider network 203 and by implementing themapping service (for traffic encapsulation and decapsulation) to relatedata plane traffic (from the data plane proxies 248) and control planetraffic (from the control plane proxies 245) to the appropriateserver(s). By implementing a local version of the provider network'ssubstrate-overlay mapping service, the local network manager(s) 242allow resources in the provider substrate extension 224 to seamlesslycommunicate with resources in the cloud provider network 203. In someimplementations, a single local network manager 242 can perform theseactions for all servers hosting compute instances in a providersubstrate extension 224. In other implementations, each of the serverhosting compute instances may have a dedicated local network manager242. In multi-rack edge locations, inter-rack communications can gothrough the local network managers 242, with local network managersmaintaining open tunnels to one another.

Provider substrate extension locations can utilize secure networkingtunnels through the provider substrate extension 224 network to thecloud provider network 203, for example, to maintain security ofcustomer data when traversing the provider substrate extension 224network and any other intermediate network (which may include the publicinternet). Within the cloud provider network 203, these tunnels arecomposed of virtual infrastructure components including isolated virtualnetworks (e.g., in the overlay network), control plane proxies 245, dataplane proxies 248, and substrate network interfaces. Such proxies 245,248 may be implemented as containers running on compute instances. Insome embodiments, each server in a provider substrate extension 224location that hosts compute instances can utilize at least two tunnels:one for control plane traffic (e.g., Constrained Application Protocol(CoAP) traffic) and one for encapsulated data plane traffic. Aconnectivity manager (not shown) within the cloud provider network 203manages the cloud provider network-side lifecycle of these tunnels andtheir components, for example, by provisioning them automatically whenneeded and maintaining them in a healthy operating state. In someembodiments, a direct connection between a provider substrate extension224 location and the cloud provider network 203 can be used for controland data plane communications. As compared to a VPN through othernetworks, the direct connection can provide constant bandwidth and moreconsistent network performance because of its relatively fixed andstable network path.

A control plane (CP) proxy 245 can be provisioned in the cloud providernetwork 203 to represent particular host(s) in an edge location. CPproxies 245 are intermediaries between the control plane 218 in thecloud provider network 203 and control plane targets in the controlplane 236 of provider substrate extension 224. That is, CP proxies 245provide infrastructure for tunneling management API traffic destined forprovider substrate extension servers out of the region substrate and tothe provider substrate extension 224. For example, a virtualizedcomputing service of the cloud provider network 203 can issue a commandto a VMM of a server of a provider substrate extension 224 to launch acompute instance. A CP proxy 245 maintains a tunnel (e.g., a VPN) to alocal network manager 242 of the provider substrate extension. Thesoftware implemented within the CP proxies 245 ensures that onlywell-formed API traffic leaves from and returns to the substrate. CPproxies 245 provide a mechanism to expose remote servers on the cloudprovider substrate while still protecting substrate security materials(e.g., encryption keys, security tokens) from leaving the cloud providernetwork 203. The one-way control plane traffic tunnel imposed by the CPproxies 245 also prevents any (potentially compromised) devices frommaking calls back to the substrate. CP proxies 245 may be instantiatedone-for-one with servers at a provider substrate extension 224 or may beable to manage control plane traffic for multiple servers in the sameprovider substrate extension.

A data plane (DP) proxy 248 can also be provisioned in the cloudprovider network 203 to represent particular server(s) in a providersubstrate extension 224. The DP proxy 248 acts as a shadow or anchor ofthe server(s) and can be used by services within the cloud providernetwork 203 to monitor the health of the host (including itsavailability, used/free compute and capacity, used/free storage andcapacity, and network bandwidth usage/availability). The DP proxy 248also allows isolated virtual networks to span provider substrateextensions 224 and the cloud provider network 203 by acting as a proxyfor server(s) in the cloud provider network 203. Each DP proxy 248 canbe implemented as a packet-forwarding compute instance or container. Asillustrated, each DP proxy 248 can maintain a VPN tunnel with a localnetwork manager 242 that manages traffic to the server(s) that the DPproxy 248 represents. This tunnel can be used to send data plane trafficbetween the provider substrate extension server(s) and the cloudprovider network 203. Data plane traffic flowing between a providersubstrate extension 224 and the cloud provider network 203 can be passedthrough DP proxies 248 associated with that provider substrate extension224. For data plane traffic flowing from a provider substrate extension224 to the cloud provider network 203, DP proxies 248 can receiveencapsulated data plane traffic, validate it for correctness, and allowit to enter into the cloud provider network 203. DP proxies 248 canforward encapsulated traffic from the cloud provider network 203directly to a provider substrate extension 224.

Local network manager(s) 242 can provide secure network connectivitywith the proxies 245, 248 established in the cloud provider network 203.After connectivity has been established between the local networkmanager(s) 242 and the proxies 245, 248, customers may issue commandsvia the interface 206 to instantiate compute instances (and/or performother operations using compute instances) using provider substrateextension resources in a manner analogous to the way in which suchcommands would be issued with respect to compute instances hosted withinthe cloud provider network 203. From the perspective of the customer,the customer can now seamlessly use local resources within a providersubstrate extension (as well as resources located in the cloud providernetwork 203, if desired). The compute instances set up on a server at aprovider substrate extension 224 may communicate both with electronicdevices located in the same network, as well as with other resourcesthat are set up in the cloud provider network 203, as desired. A localgateway 251 can be implemented to provide network connectivity between aprovider substrate extension 224 and a network associated with theextension (e.g., a communications service provider network in theexample of a communications service provider substrate extension 230).

There may be circumstances that necessitate the transfer of data betweenthe object storage service and a provider substrate extension (PSE) 224.For example, the object storage service may store machine images used tolaunch VMs, as well as snapshots representing point-in-time backups ofvolumes. The object gateway can be provided on a PSE server or aspecialized storage device, and provide customers with configurable,per-bucket caching of object storage bucket contents in their PSE 224 tominimize the impact of PSE-region latency on the customer's workloads.The object gateway can also temporarily store snapshot data fromsnapshots of volumes in the PSE 224 and then sync with the objectservers in the region when possible. The object gateway can also storemachine images that the customer designates for use within the PSE 224or on the customer's premises. In some implementations, the data withinthe PSE 224 may be encrypted with a unique key, and the cloud providercan limit keys from being shared from the region to the PSE 224 forsecurity reasons. Accordingly, data exchanged between the object storeservers and the object gateway may utilize encryption, decryption,and/or re-encryption in order to preserve security boundaries withrespect to encryption keys or other sensitive data. The transformationintermediary can perform these operations, and a PSE bucket can becreated (on the object store servers) to store snapshot data and machineimage data using the PSE encryption key.

In the manner described above, a PSE 224 forms an edge location, in thatit provides the resources and services of the cloud provider network 203outside of a traditional cloud provider data center and closer tocustomer devices. An edge location, as referred to herein, can bestructured in several ways. In some implementations, an edge locationcan be an extension of the cloud provider network substrate including alimited quantity of capacity provided outside of an availability zone(e.g., in a small data center or other facility of the cloud providerthat is located close to a customer workload and that may be distantfrom any availability zones). Such edge locations may be referred to as“far zones” (due to being far from other availability zones) or “nearzones” (due to being near to customer workloads). A near zone may beconnected in various ways to a publicly accessible network such as theInternet, for example directly, via another network, or via a privateconnection to a region. Although typically a near zone would have morelimited capacity than a region, in some cases a near zone may havesubstantial capacity, for example thousands of racks or more.

In some implementations, an edge location may be an extension of thecloud provider network substrate formed by one or more servers locatedon-premise in a customer or partner facility, wherein such server(s)communicate over a network (e.g., a publicly-accessible network such asthe Internet) with a nearby availability zone or region of the cloudprovider network. This type of substrate extension located outside ofcloud provider network data centers can be referred to as an “outpost”of the cloud provider network. Some outposts may be integrated intocommunications networks, for example as a multi-access edge computing(MEC) site having physical infrastructure spread acrosstelecommunication data centers, telecommunication aggregation sites,and/or telecommunication base stations within the telecommunicationnetwork. In the on-premise example, the limited capacity of the outpostmay be available for use only by the customer who owns the premises (andany other accounts allowed by the customer). In the telecommunicationsexample, the limited capacity of the outpost may be shared amongst anumber of applications (e.g., games, virtual reality applications,healthcare applications) that send data to users of thetelecommunications network.

An edge location can include data plane capacity controlled at leastpartly by a control plane of a nearby availability zone of the providernetwork. As such, an availability zone group can include a “parent”availability zone and any “child” edge locations homed to (e.g.,controlled at least partly by the control plane of) the parentavailability zone. Certain limited control plane functionality (e.g.,features that require low latency communication with customer resources,and/or features that enable the edge location to continue functioningwhen disconnected from the parent availability zone) may also be presentin some edge locations. Thus, in the above examples, an edge locationrefers to an extension of at least data plane capacity that ispositioned at the edge of the cloud provider network, close to customerdevices and/or workloads.

In the example of FIG. 1A, the distributed computing devices 112 (FIG.1A), the centralized computing devices 115 (FIG. 1A), and the corecomputing devices 118 (FIG. 1A) may be implemented as provider substrateextensions 224 of the cloud provider network 203. The installation orsiting of provider substrate extensions 224 within a communicationnetwork 100 can vary subject to the particular network topology orarchitecture of the communication network 100. Provider substrateextensions 224 can generally be connected anywhere the communicationnetwork 100 can break out packet-based traffic (e.g., IP based traffic).Additionally, communications between a given provider substrateextension 224 and the cloud provider network 203 typically securelytransit at least a portion of the communication network 100 (e.g., via asecure tunnel, virtual private network, a direct connection, etc.).

In 5G wireless network development efforts, edge locations may beconsidered a possible implementation of Multi-access Edge Computing(MEC). Such edge locations can be connected to various points within a5G network that provide a breakout for data traffic as part of the UserPlane Function (UPF). Older wireless networks can incorporate edgelocations as well. In 3G wireless networks, for example, edge locationscan be connected to the packet-switched network portion of acommunication network 100, such as to a Serving General Packet RadioServices Support Node (SGSN) or to a Gateway General Packet RadioServices Support Node (GGSN). In 4G wireless networks, edge locationscan be connected to a Serving Gateway (SGW) or Packet Data NetworkGateway (PGW) as part of the core network or evolved packet core (EPC).In some embodiments, traffic between a provider substrate extension 224and the cloud provider network 203 can be broken out of thecommunication network 100 without routing through the core network.

In some embodiments, provider substrate extensions 224 can be connectedto more than one communication network associated with respectivecustomers. For example, when two communication networks of respectivecustomers share or route traffic through a common point, a providersubstrate extension 224 can be connected to both networks. For example,each customer can assign some portion of its network address space tothe provider substrate extension, and the provider substrate extensioncan include a router or gateway that can distinguish traffic exchangedwith each of the communication networks 100. For example, trafficdestined for the provider substrate extension 224 from one network mighthave a different destination IP address, source IP address, and/orvirtual local area network (VLAN) tag than traffic received from anothernetwork. Traffic originating from the provider substrate extension to adestination on one of the networks can be similarly encapsulated to havethe appropriate VLAN tag, source IP address (e.g., from the poolallocated to the provider substrate extension from the destinationnetwork address space) and destination IP address.

FIG. 2B depicts an example 253 of cellularization and geographicdistribution of the communication network 100 (FIG. 1A) for providinghighly available user plane functions (UPFs). In FIG. 2B, a user device254 communicates with a request router 255 to route a request to one ofa plurality of control plane cells 257 a and 257 b. Each control planecell 257 may include a network service API gateway 260, a network sliceconfiguration 262, a function for network service monitoring 264, siteplanning data 266 (including layout, device type, device quantities,etc. that describe a customer's site requirements), a networkservice/function catalog 268, a function for orchestration 270, and/orother components. The larger control plane can be divided into cells inorder to reduce the likelihood that large scale errors will affect awide range of customers, for example by having one or more cells percustomer, per network, or per region that operate independently.

The network service/function catalog 268 is also referred to as the NFRepository Function (NRF). In a Service Based Architecture (SBA) 5Gnetwork, the control plane functionality and common data repositoriescan be delivered by way of a set of interconnected network functionsbuilt using a microservices architecture. The NRF can maintain a recordof available NF instances and their supported services, allowing otherNF instances to subscribe and be notified of registrations from NFinstances of a given type. The NRF thus can support service discovery byreceipt of discovery requests from NF instances, and details which NFinstances support specific services. The network function orchestrator270 can perform NF lifecycle management including instantiation,scale-out/in, performance measurements, event correlation, andtermination. The network function orchestrator 270 can also onboard newNFs, manage migration to new or updated versions of existing NFs,identify NF sets that are suitable for a particular network slice orlarger network, and orchestrate NFs across different computing devicesand sites that make up the radio-based private network 103.

The control plane cell 257 may be in communication with one or more cellsites 272, one or more customer local data centers 274, one or morelocal zones 276, and one or more regional zones 278. The cell sites 272include computing hardware 280 that executes one or more distributedunit (DU) network functions 282. The customer local data centers 274include computing hardware 283 that execute one or more DU or centralunit (CU) network functions 284, a network controller 285, a UPF 286,one or more edge applications 287 corresponding to customer workloads,and/or other components.

The local zones 276, which may be in a data center operated by a cloudservice provider, may execute one or more core network functions 288,such as an AMF, an SMF, a network exposure function (NEF) that securelyexposes the services and capabilities of other network functions, aunified data management (UDM) function that manages subscriber data forauthorization, registration, and mobility management. The local zones276 may also execute a UPF 286, a service for metric processing 289, andone or more edge applications 287.

The regional zones 278, which may be in a data center operated by acloud service provider, may execute one or more core network functions288; a UPF 286; an operations support system (OSS) 290 that supportsnetwork management systems, service delivery, service fulfillment,service assurance, and customer care; an internet protocol multimediasubsystem (IMS) 291; a business support system (BSS) 292 that supportsproduct management, customer management, revenue management, and/ororder management; one or more portal applications 293, and/or othercomponents.

In this example, the communication network 100 employs a cellulararchitecture to reduce the blast radius of individual components. At thetop level, the control plane is in multiple control plane cells 257 toprevent an individual control plane failure from impacting alldeployments.

Within each control plane cell 257, multiple redundant stacks can beprovided with the control plane shifting traffic to secondary stacks asneeded. For example, a cell site 272 may be configured to utilize anearby local zone 276 as its default core network. In the event that thelocal zone 276 experiences an outage, the control plane can redirect thecell site 272 to use the backup stack in the regional zone 278. Trafficthat would normally be routed from the internet to the local zone 276can be shifted to endpoints for the regional zones 278. Each controlplane cell 257 can implement a “stateless” architecture that shares acommon session database across multiple sites (such as acrossavailability zones or edge sites).

FIG. 3A illustrates an exemplary cloud provider network 203 includinggeographically dispersed provider substrate extensions 224 (FIG. 2A) (or“edge locations 303”) according to some embodiments. As illustrated, acloud provider network 203 can be formed as a number of regions 306,where a region is a separate geographical area in which the cloudprovider has one or more data centers 309. Each region 306 can includetwo or more availability zones (AZs) connected to one another via aprivate high-speed network such as, for example, a fiber communicationconnection. An availability zone refers to an isolated failure domainincluding one or more data center facilities with separate power,separate networking, and separate cooling relative to other availabilityzones. A cloud provider may strive to position availability zones withina region far enough away from one another such that a natural disaster,widespread power outage, or other unexpected event does not take morethan one availability zone offline at the same time. Customers canconnect to resources within availability zones of the cloud providernetwork via a publicly accessible network (e.g., the Internet, acellular communication network, a communication service providernetwork). Transit Centers (TC) are the primary backbone locationslinking customers to the cloud provider network and may be co-located atother network provider facilities (e.g., Internet service providers,telecommunications providers). Each region can operate two or more TCsfor redundancy. Regions 306 are connected to a global network whichincludes private networking infrastructure (e.g., fiber connectionscontrolled by the cloud service provider) connecting each region 306 toat least one other region. The cloud provider network 203 may delivercontent from points of presence (PoPs) outside of, but networked with,these regions 306 by way of edge locations 303 and regional edge cacheservers. This compartmentalization and geographic distribution ofcomputing hardware enables the cloud provider network 203 to providelow-latency resource access to customers on a global scale with a highdegree of fault tolerance and stability.

In comparison to the number of regional data centers or availabilityzones, the number of edge locations 303 can be much higher. Suchwidespread deployment of edge locations 303 can provide low-latencyconnectivity to the cloud for a much larger group of end user devices(in comparison to those that happen to be very close to a regional datacenter). In some embodiments, each edge location 303 can be peered tosome portion of the cloud provider network 203 (e.g., a parentavailability zone or regional data center). Such peering allows thevarious components operating in the cloud provider network 203 to managethe compute resources of the edge location 303. In some cases, multipleedge locations 303 may be sited or installed in the same facility (e.g.,separate racks of computer systems) and managed by different zones ordata centers to provide additional redundancy. Note that although edgelocations 303 are typically depicted herein as within a communicationservice provider network or a radio-based private network 103 (FIG. 1A),in some cases, such as when a cloud provider network facility isrelatively close to a communications service provider facility, the edgelocation 303 can remain within the physical premises of the cloudprovider network 203 while being connected to the communications serviceprovider network via a fiber or other network link.

An edge location 303 can be structured in several ways. In someimplementations, an edge location 303 can be an extension of the cloudprovider network substrate including a limited quantity of capacityprovided outside of an availability zone (e.g., in a small data centeror other facility of the cloud provider that is located close to acustomer workload and that may be distant from any availability zones).Such edge locations 303 may be referred to as local zones (due to beingmore local or proximate to a group of users than traditionalavailability zones). A local zone may be connected in various ways to apublicly accessible network such as the Internet, for example directly,via another network, or via a private connection to a region 306.Although typically a local zone would have more limited capacity than aregion 306, in some cases a local zone may have substantial capacity,for example thousands of racks or more. Some local zones may use similarinfrastructure as typical cloud provider data centers, instead of theedge location 303 infrastructure described herein.

As indicated herein, a cloud provider network 203 can be formed as anumber of regions 306, where each region 306 represents a geographicalarea in which the cloud provider clusters data centers. Each region 306can further include multiple (e.g., two or more) availability zones(AZs) connected to one another via a private high-speed network, forexample, a fiber communication connection. An AZ may provide an isolatedfailure domain including one or more data center facilities withseparate power, separate networking, and separate cooling from those inanother AZ. Preferably, AZs within a region 306 are positioned farenough away from one another such that a same natural disaster (or otherfailure-inducing event) should not affect or take more than one AZoffline at the same time. Customers can connect to an AZ of the cloudprovider network via a publicly accessible network (e.g., the Internet,a cellular communication network).

The parenting of a given edge location 303 to an AZ or region 306 of thecloud provider network 203 can be based on a number of factors. One suchparenting factor is data sovereignty. For example, to keep dataoriginating from a communication network in one country within thatcountry, the edge locations 303 deployed within that communicationnetwork can be parented to AZs or regions 306 within that country.Another factor is availability of services. For example, some edgelocations 303 may have different hardware configurations such as thepresence or absence of components such as local non-volatile storage forcustomer data (e.g., solid state drives), graphics accelerators, etc.Some AZs or regions 306 might lack the services to exploit thoseadditional resources, thus, an edge location could be parented to an AZor region 306 that supports the use of those resources. Another factoris the latency between the AZ or region 306 and the edge location 303.While the deployment of edge locations 303 within a communicationnetwork has latency benefits, those benefits might be negated byparenting an edge location 303 to a distant AZ or region 306 thatintroduces significant latency for the edge location 303 to regiontraffic. Accordingly, edge locations 303 are often parented to nearby(in terms of network latency) AZs or regions 306.

FIG. 3B depicts a state diagram 320 for creation and management of aradio-based private network 103 (FIG. 1A). Beginning with created state322, a representation of the radio-based private network 103 is createdin response to a customer request via a user interface or API call. Ifthe customer then requests to activate the radio-based private network103, the radio-based private network 103 transitions to the pendingstate 324. At this point, the radio-based private network 103 isconsidered locked such that configuration changes to the radio-basedprivate network 103 cannot be made.

Within the pending state 324, the radio-based private network 103 movesto the deploying state 326, where radio units, DU/CU hardware, and insome cases edge computing hardware are ordered and preconfigured for usein the radio-based private network 103. Next, the radio-based privatenetwork 103 continues to the shipping state 328 where the preconfiguredhardware is shipped to the customer's site. Other hardware such asantennas, tower components, network routers, cabling, and so on, may beshipped to the customer's site as part of the shipment. In someembodiments, subscriber identity modules (SIMs) for the wireless devices106 (FIG. 1A) may also be shipped. Once the shipment is delivered, theradio-based private network 103 moves to the delivered state 330.Meanwhile, one or more resources for the core network 118 (FIG. 1A) maybe provisioned and configured within a cloud provider network 203 (FIG.2A) to support the radio-based private network 103.

Upon connection of the hardware, the radio-based private network 103 maythen move to the activated state 332. In the activated state 332, theradio-based private network 103 is online and available to provideconnectivity for wireless devices 106 that have been configured foraccess to the radio-based private network 103. While in the activatedstate 332, a customer may request a change to update the radio-basedprivate network 103, such as to request additional or differenthardware, thereby causing the radio-based private network 103 to reenterthe pending state 324. Alternatively, the customer may request to deletethe radio-based private network 103 from the activated state 332,causing the radio-based private network 103 to become deactivated andenter the deleted state 336.

If any of the processes fail in the pending state 324, the radio-basedprivate network 103 may enter the deactivated state 338. From thedeactivated state 338, the customer may update the radio-based privatenetwork 103 to address the failure, thereby reentering the pending state324. The customer may instead request that the radio-based privatenetwork 103 be deleted, which causes the radio-based private network 103to enter the deleted state 336. The customer may also cause theradio-based private network 103 to enter the deleted state 336 from thecreated state 322, if the customer chooses not to activate theradio-based private network 103.

With reference to FIG. 4 , shown is a networked environment 400according to various embodiments. The networked environment 400 includesa computing environment 403, one or more client devices 406, one or morevendor computing devices 408, one or more predeployed devices 409, aspectrum reservation service 410, and one or more radio-based privatenetworks 103, which are in data communication with each other via anetwork 412. The network 412 includes, for example, the Internet,intranets, extranets, wide area networks (WANs), local area networks(LANs), wired networks, wireless networks, cable networks, satellitenetworks, or other suitable networks, etc., or any combination of two ormore such networks.

The computing environment 403 may comprise, for example, a servercomputer or any other system providing computing capacity.Alternatively, the computing environment 403 may employ a plurality ofcomputing devices that may be arranged, for example, in one or moreserver banks or computer banks or other arrangements. Such computingdevices may be located in a single installation or may be distributedamong many different geographical locations. For example, the computingenvironment 403 may include a plurality of computing devices thattogether may comprise a hosted computing resource, a grid computingresource, and/or any other distributed computing arrangement. In somecases, the computing environment 403 may correspond to an elasticcomputing resource where the allotted capacity of processing, network,storage, or other computing-related resources may vary over time. Forexample, the computing environment 403 may correspond to a cloudprovider network 203 (FIG. 2A), where customers are billed according totheir computing resource usage based on a utility computing model.

In some embodiments, the computing environment 403 may correspond to avirtualized private network within a physical network comprising virtualmachine instances executed on physical computing hardware, e.g., by wayof a hypervisor. The virtual machine instances and any containersrunning on these instances may be given network connectivity by way ofvirtualized network components enabled by physical network components,such as routers and switches.

Various applications and/or other functionality may be executed in thecomputing environment 403 according to various embodiments. Also,various data is stored in a data store 415 that is accessible to thecomputing environment 403. The data store 415 may be representative of aplurality of data stores 415 as can be appreciated. The data stored inthe data store 415, for example, is associated with the operation of thevarious applications and/or functional entities described below.

The computing environment 403 as part of a cloud provider networkoffering utility computing services includes computing devices 418 andother types of computing devices. The computing devices 418 maycorrespond to different types of computing devices 418 and may havedifferent computing architectures. The computing architectures maydiffer by utilizing processors having different architectures, such asx86, x86_64, ARM, Scalable Processor Architecture (SPARC), PowerPC, andso on. For example, some computing devices 418 may have x86 processors,while other computing devices 418 may have ARM processors. The computingdevices 418 may differ also in hardware resources available, such aslocal storage, graphics processing units (GPUs), machine learningextensions, and other characteristics.

The computing devices 418 may have various forms of allocated computingcapacity 421, which may include virtual machine (VM) instances,containers, serverless functions, and so forth. The VM instances may beinstantiated from a VM image. To this end, customers may specify that avirtual machine instance should be launched in a particular type ofcomputing devices 418 as opposed to other types of computing devices418. In various examples, one VM instance may be executed singularly ona particular computing device 418, or a plurality of VM instances may beexecuted on a particular computing device 418. Also, a particularcomputing device 418 may execute different types of VM instances, whichmay offer different quantities of resources available via the computingdevice 418. For example, some types of VM instances may offer morememory and processing capability than other types of VM instances.

The components executed on the computing environment 403, for example,include a radio-based private network (RBPN) management API 423, a RBPNmanagement service 424, a radio unit management service 427, and otherapplications, services, processes, systems, engines, or functionalitynot discussed in detail herein.

The RBPN management API 423 provides interfaces for creating, deploying,activating, managing, updating, deactivating, and deleting radio-basedprivate networks 103. In various embodiments, the RBPN management API423 may implement functions for creating a site or location, describinga site, deleting a site, updating a site, creating a network plan,describing a network plan, updating a network plan, deleting a networkplan, creating a network, describing a network, listing networksassociated with a customer, deleting a network, activating a network,creating a data plan, describing a data plan, listing data plans for anetwork, attaching a SIM or eSIM to a data plan, deleting a data plan,listing SIMs or eSIMs associated with a network, configuring a smallcell or radio unit installation either singularly or as a batch, andother functions.

The RBPN management service 424 is executed to manage, configure, andmonitor radio-based private networks 103 that are operated by a cloudservice provider on behalf of customers. To this end, the RBPNmanagement service 424 may generate a number of user interfaces thatallow customers to place orders for new radio-based private networks103, scale up or scale down existing radio-based private networks 103,modify the operation of existing radio-based private networks 103,configure wireless devices 106 (FIG. 1A) that are permitted to use theradio-based private networks 103, provide statistics and metricsregarding the operation of radio-based private networks 103, reservefrequency spectrum for customer's private networks via a spectrumreservation service 410, and so on. For example, the RBPN managementservice 424 may generate one or more network pages, such as web pages,that include the user interfaces. Also, the RBPN management service 424may support this functionality by way of an API that may be called by aclient application 436. The RBPN management service 424 may use the RBPNmanagement API 423 to implement the various actions. In addition tofacilitating interaction with users, the RBPN management service 424also implements orchestration of deployments and configuration changesfor the radio-based private networks 103 and on-going monitoring ofperformance parameters. For a particular site 438, the RBPN managementservice 424 may generate a network plan 439 for a customer based atleast in part in a specification of the customer's location in the site438, an automated site survey by an unmanned aerial vehicle, and/orother input parameters.

The radio unit management service 427 is executed to implementprovisioning and configuration changes on hardware that implements aradio-based private network 103. This may include radio units, antennas,VM instances or containers that perform network functions, routers,switches, fiber termination equipment, and so on. For example, antennasmay be configured for operation at specific frequencies. Radio units maybe programmed to operate at specific frequencies, join a particularradio-based private network 103, and backhaul traffic to a particular VMinstance or container.

In some scenarios, the radio unit management service 427 is executed toreconfigure hardware already present in a radio-based private network103. In other scenarios, the radio unit management service 427 isexecuted to preconfigure hardware set to be deployed to existing or newradio-based private networks 103. To this end, the radio unit managementservice 427 may implement configurations on one or more predeployeddevices 409 that are temporarily connected to the network 412 tofacilitate preconfiguration before the predeployed devices 409 areshipped to the customer for deployment in the radio-based privatenetworks 103.

The RBPN management service 424 may also automate and arrange deploymentof hardware to implement a radio-based private network 103. Based on anetwork plan 439 submitted by or generated for a customer, the RBPNmanagement service 424 may arrange procurement for the hardwarecomponents from one or more vendors associated with the vendor computingdevices 408 necessary to implement a radio-based private network 103according to the network plan 439. This may involve placing orders fornew equipment automatically from vendors via the vendor computingdevices 408, reserving equipment already within inventory of theprovider, or reallocating equipment already present at the customer'ssite or sites of other customers, where the equipment to be reallocatedis no longer utilized. In this regard, the RBPN management service 424may send a directive to customers to return equipment that is no longerutilized, where the equipment may be sent directly to other customersfor use in another deployment. In another scenario, the RBPN managementservice 424 may send a directive to a customer to move a piece ofequipment from one site where the equipment is no longer used to anothersite where the equipment will be used. The RBPN management service 424may manage connection of equipment to the network 412 forpreconfiguration as a predeployed device 409. The RBPN managementservice 424 may also arrange shipping of equipment to customerlocations, including potentially a plurality of locations of thecustomer corresponding to respective cell sites.

The data stored in the data store 415 includes, for example, one or moresites 438, one or more network plans 439, one or more data plans 440,one or more cellular topologies 442, one or more spectrum assignments445, device data 448, one or more RBPN metrics 451, customer billingdata 454, radio unit configuration data 457, antenna configuration data460, network function configuration data 463, one or more networkfunction workloads 466, one or more customer workloads 469, andpotentially other data.

A site 438 represents a specification of a location at which aradio-based private network 103 is to be deployed for a customer. In oneimplementation, the site 438 is created by way of the RBPN managementAPI 423 through the specification of a site name and an address.Latitude and longitude coordinates may be used in other examples. TheRBPN management API 423 may associate a unique site identifier with thesite 438.

The network plan 439 is a specification of a radio-based private network103 to be deployed for a customer. In various implementations, a networkplan 439 may include one or more identifiers of sites 438, premises,locations, or geographic areas to be covered, a quantity of cells, amaximum number of wireless devices 106 per cell, a quantity of wirelessdevices 106 or SIMs, device identification information and permissions,a desired measure of edge computing capacity in the radio-based privatenetwork 103, a desired maximum network latency, a desired bandwidth ornetwork throughput for one or more classes of devices, one or morequality of service parameters for applications or services, a range ofnetwork addresses to be assigned to the wireless devices 106, anidentifier of a type of spectrum to be used (e.g., Citizens BroadbandRadio Service, television whitespaces, licensed spectrum, etc.), and/orother parameters that can be used to create a radio-based privatenetwork 103. A customer may manually specify one or more of theseparameters via a user interface or an API. One or more of the parametersmay be prepopulated as default parameters. In some cases, a network plan439 may be generated for a customer based at least in part on automatedsite surveys using unmanned aerial vehicles. In some cases, the networkplan 439 may incorporate thresholds and reference parameters determinedat least in part on an automated probe of an existing private network ofa customer.

The data plans 440 may correspond to one or more plans for accessing aradio-based private network 103 from wireless devices 106. A data plan440 may include a network identifier, a data plan name, an uplink speed,a downlink speed, a unique identifier of the data plan 440, latencyrequirements, jitter requirements, and/or other data. Values of theparameters that define the data plans 440 may be used as a basis for acloud service provider billing the customer under a utility computingmodel. For example, the customer may be billed a higher amount for lowerlatency targets and/or higher bandwidth targets in a service-levelagreement (SLA), and the customer can be charged on a per-device basis,a per-cell basis, based on a geographic area served, based on spectrumavailability, etc.

The cellular topology 442 includes an arrangement of a plurality ofcells for a customer that takes into account reuse of frequency spectrumwhere possible given the location of the cells. The cellular topology442 may be automatically generated given a site survey. In some cases,the number of cells in the cellular topology 442 may be automaticallydetermined based on a desired geographic area to be covered,availability of backhaul connectivity at various sites, signalpropagation, available frequency spectrum, and/or on other parameters.For radio-based private networks 103, the cellular topology 442 may bedeveloped to cover one or more buildings in an organizational campus,one or more schools in a school district, one or more buildings in auniversity or university system, and other areas.

The spectrum assignments 445 include frequency spectrum that isavailable to be allocated for radio-based private networks 103 as wellas frequency spectrum that is currently allocated to radio-based privatenetworks 103. The frequency spectrum may include spectrum that ispublicly accessible without restriction, spectrum that is individuallyowned or leased by customers, spectrum that is owned or leased by theprovider, spectrum that is free to use but requires reservation, and soon.

The device data 448 corresponds to data describing wireless devices 106that are permitted to connect to the radio-based private network 103.This device data 448 includes corresponding users, account information,billing information, data plan 440, permitted applications or uses, anindication of whether the wireless device 106 is mobile or fixed, alocation, a current cell, a network address, device identifiers (e.g.,International Mobile Equipment Identity (IMEI) number, InternationalMobile Subscriber Identity (IMSI) numbers, Equipment Serial Number(ESN), Media Access Control (MAC) address, Subscriber Identity Module(SIM) number, embedded SIM (eSIM) number, etc.), and so on.

The RBPN metrics 451 include various metrics or statistics that indicatethe performance or health of the radio-based private network 103. SuchRBPN metrics 451 may include bandwidth metrics, dropped packet metrics,signal strength metrics, latency metrics, and so on. The RBPN metrics451 may be aggregated on a per-device basis, a per-cell basis, aper-customer basis, etc.

The customer billing data 454 specifies charges that the customer is toincur for the operation of the radio-based private network 103 for thecustomer by the provider. The charges may include fixed costs based uponequipment deployed to the customer and/or usage costs based uponutilization as determined by usage metrics that are tracked. In somecases, the customer may purchase the equipment up-front and may becharged only for bandwidth or backend network costs. In other cases, thecustomer may incur no up-front costs and may be charged purely based onutilization. With the equipment being provided to the customer based ona utility computing model, the cloud service provider may choose anoptimal configuration of equipment in order to meet customer targetperformance metrics while avoiding overprovisioning of unnecessaryhardware.

The radio unit configuration data 457 may correspond to configurationsettings for radio units deployed in radio-based private networks 103.Such settings may include frequencies to be used, protocols to be used,modulation parameters, bandwidth, network routing and/or backhaulconfiguration, location, and height for the radio unit, and so on.

The antenna configuration data 460 may correspond to configurationsettings for antennas, to include frequencies to be used, azimuth,vertical or horizontal orientation, beam tilt, height, and/or otherparameters that may be controlled automatically (e.g., bynetwork-connected motors and controls on the antennas) or manually bydirecting a user to mount the antenna in a certain way or make aphysical change to the antenna.

The network function configuration data 463 corresponds to configurationsettings that configure the operation of various network functions forthe radio-based private network 103. In various embodiments, the networkfunctions may be deployed in VM instances or containers located incomputing devices 418 that are at cell sites, at customer aggregationsites, or in data centers remotely located from the customer.Non-limiting examples of network functions may include an access andmobility management function, a session management function, a userplane function, a policy control function, an authentication serverfunction, a unified data management function, an application function, anetwork exposure function, a network function repository, a networkslice selection function, and/or others. The network function workloads466 correspond to machine images, containers, or functions to belaunched in the allocated computing capacity 421 to perform one or moreof the network functions.

The customer workloads 469 correspond to machine images, containers, orfunctions of the customer that may be executed alongside or in place ofthe network function workloads 466 in the allocated computing capacity421. For example, the customer workloads 469 may provide or support acustomer application or service. In various examples, the customerworkloads 469 relate to factory automation, autonomous robotics,augmented reality, virtual reality, design, surveillance, and so on.

The client device 406 is representative of a plurality of client devices406 that may be coupled to the network 412. The client device 406 maycomprise, for example, a processor-based system such as a computersystem. Such a computer system may be embodied in the form of a desktopcomputer, a laptop computer, personal digital assistants, cellulartelephones, smartphones, set-top boxes, music players, web pads, tabletcomputer systems, game consoles, electronic book readers, smartwatches,head mounted displays, voice interface devices, or other devices. Theclient device 406 may include a display comprising, for example, one ormore devices such as liquid crystal display (LCD) displays, gasplasma-based flat panel displays, organic light emitting diode (OLED)displays, electrophoretic ink (E ink) displays, LCD projectors, or othertypes of display devices, etc.

The client device 406 may be configured to execute various applicationssuch as a client application 436 and/or other applications. The clientapplication 436 may be executed in a client device 406, for example, toaccess network content served up by the computing environment 403 and/orother servers, thereby rendering a user interface on the display. Tothis end, the client application 436 may comprise, for example, abrowser, a dedicated application, etc., and the user interface maycomprise a network page, an application screen, etc. The client device406 may be configured to execute applications beyond the clientapplication 436 such as, for example, email applications, socialnetworking applications, word processors, spreadsheets, and/or otherapplications.

In some embodiments, the spectrum reservation service 410 providesreservations of frequency spectrum for customers' private networks. Inone scenario, the spectrum reservation service 410 is operated by anentity, such as a third party, to manage reservations and coexistence inpublicly accessible spectrum. One example of such spectrum may be theCitizens Broadband Radio Service (CBRS). In another scenario, thespectrum reservation service 410 is operated by a telecommunicationsservice provider in order to sell or sublicense portions of spectrumowned or licensed by the provider.

Referring next to FIG. 5 , shown is a flowchart that provides oneexample of the operation of a portion of the RBPN management service 424according to various embodiments. It is understood that the flowchart ofFIG. 5 provides merely an example of the many different types offunctional arrangements that may be employed to implement the operationof the portion of the RBPN management service 424 as described herein.As an alternative, the flowchart of FIG. 5 may be viewed as depicting anexample of elements of a method implemented in the computing environment403 (FIG. 4 ) according to one or more embodiments.

Beginning with box 503, the RBPN management service 424 receives arequest to create a site 438 (FIG. 4 ) for a radio-based private network103 (FIG. 1A). The request may be received via the RBPN management API423 (FIG. 4 ) or by way of a user interface generated by the RBPNmanagement service 424. Before the request is received, the RBPNmanagement service 424 may authenticate the customer for access to anaccount associated with a cloud service provider and ensure that theaccount has access to the RBPN management API 423. In this regard, theRBPN management service 424 may operate based on the access controlsystem of the cloud service provider. Further, the RBPN managementservice 424 may integrate one or more additional cloud services offeredby the cloud service provider. Accordingly, the customer may launchcloud services from the cloud service provider to be executed on edgecomputing capacity deployed in the radio-based private network 103. Inone such example, the customer may utilize a video stream processingservice from the cloud service provider to process video streamscaptured by cameras on wireless devices 106.

The request to create a site 438 may specify a site name and a locationin terms of an address or latitude/longitude coordinates. In box 506,the RBPN management service 424 generates a unique site identifier andcreates the site 438. The RBPN management service 424 may then returnthe site identifier to the customer.

In box 507, the RBPN management service 424 receives a request to createa network plan 439 (FIG. 4 ). The request may be received via the RBPNmanagement API 423 or by way of a user interface generated by the RBPNmanagement service 424. For example, the request may specify a networkplan name, a quantity of wireless devices 106 (FIG. 1A) or SIMs, anetwork address range for the wireless devices 106, a number of radiounits or cells, a maximum number of wireless devices 106 per cell orradio unit, a measure of edge computing capacity to be deployed on site438 (e.g., a quantity of a particular type of edge computing device), atype of spectrum to be used (e.g., TV whitespaces, CBRS, Wi-Fi,communication service provider-owned spectrum), and other parameters.

In box 509, the RBPN management service 424 determines a quantity ofradio units for the network plan 439 (FIG. 4 ). In some cases, thequantity of radio units may be a customer-supplied parameter.Alternatively, the RBPN management service 424 may determine thequantity of radio units based at least in part on the number of wirelessdevices 106 to be served, a maximum number of wireless devices 106 perradio unit or cell, a quality of service parameter, spectrumavailability at the site 438, a geographic area to be covered at thesite 438, potential interference at the site 438, and/or on otherfactors. The RBPN management service 424 may also determine types ofradio units; for example, indoor or outdoor models. In box 512, the RBPNmanagement service 424 generates a unique network plan identifier andcreates the network plan 439. The RBPN management service 424 may thenreturn the network plan identifier to the customer.

In box 515, the RBPN management service 424 receives a request to createa radio-based private network 103. The request may specify an identifierof a site 438, an identifier of a network plan 439, a type of network(e.g., 4G, 5G, 6G, Wi-Fi, etc.), a network name, and so forth. A defaultnetwork plan 439 with default parameters may be used if no network plan439 is specified.

In box 518, the RBPN management service 424 generates a uniqueidentifier for the radio-based private network 103 and creates arepresentation of the radio-based private network 103. The RBPNmanagement service 424 may return the identifier for the radio-basedprivate network 103 to the customer. The RBPN management service 424 mayalso return information such as an estimated time at which theradio-based private network 103 will be ready for activation, separatelyfrom any actions required of the customer to physically plug-in andconnect the hardware.

Requests may also be received to create one or more data plans 440 (FIG.4 ) for the radio-based private network 103. The requests may specify anetwork identifier, a data plan name, an uplink speed, a downlink speed,a maximum latency, a maximum jitter, and/or other parameters. Eachwireless device 106 may be associated with a particular data plan 440 inthe radio-based private network 103 for purposes of enforcingquality-of-service and billing.

In box 521, the RBPN management service 424 receives a request toactivate a radio-based private network 103. The request may specify theunique identifier corresponding to the radio-based private network 103.Upon receiving this request, the RBPN management service 424 may lockthe state of the radio-based private network 103 such that furthermodifications are not allowed while fulfillment and preconfiguration isoccurring. The RBPN management service 424 may provide status updates tothe customer, including the status of any shipments or of the network,as well as the status of any SIMs and their corresponding data plans 440and IMSI identifiers.

In box 522, the RBPN management service 424 may preconfigure hardwarefor the radio-based private network 103, to include radio units, SIMs oreSIMs, edge computing devices including DUs and CUs, routers, networkappliances, and/or other hardware. The RBPN management service 424 maypreconfigure one or more computing devices to provide edge computingcapacity as a provider substrate extension 224 (FIG. 2A) of a cloudprovider network 203 (FIG. 2A). The RBPN management service 424 maygenerate an order for hardware such as the radio units and SIMs and thentransmit the order to one or more vendor computing devices 408 (FIG. 4 )corresponding to the vendors. For example, an order for radio units mayspecify a model, quantity, and a radio unit management service 427endpoint. An order for SIMs may specify an IMSI range and a quantity. Insome implementations, eSIMs may be utilized instead of physical SIMs. Insome cases, a manual approval may be required prior to sending theorders to the vendors. The vendors may return identity provisioninginformation for configuration, including public/private keys,certificates, and/or endpoint information. Upon receipt of the hardware,the devices may be connected to the network 412 (FIG. 4 ) as predeployeddevices 409 and configuration settings may be established on thepredeployed devices 409 to implement the radio-based private network103.

In box 524, the RBPN management service 424 initiates one or moreshipments of the radio units, SIMs, and/or other hardware that has beenpreconfigured to the customer. For example, the shipments may bedirected to an address specified in the site 438, shipping labels may begenerated and manifests transmitted to one or more shipping carriers. Insome cases, shipments may be drop shipped from vendors.

In box 527, the RBPN management service 424 provisions one or morecomputing resources in the cloud provider network 203 to function as acore network 118 (FIG. 1A) for the radio-based private network 103. Thismay be timed to occur before the hardware is delivered to the customer.In some cases, the computing resources of the core network 118 may bewholly or partly provisioned on edge computing capacity at thecustomer's site within a provider substrate extension 224. The resourcesmay be in a particular region 306 (FIG. 3A) of a plurality of regions306 of the cloud provider network 203, and the customer may specify theparticular region 306. The quantity of resources may be configured basedupon the data plans 440 and the number of wireless devices 106. As partof provisioning the resources, the RBPN management service 424 mayprovision a virtual network link for control plane network traffic forthe radio access network at the customer location to the resources inthe particular region 306. The radio access network may be configuredsuch that a loss of connectivity via the virtual network link for thecontrol plane network traffic does not impact connectivity, at leastinitially, in the radio access network for connections among thewireless devices 106 of the radio access network with other wirelessdevices 103 of the radio access network.

In box 530, the RBPN management service 424 activates the radio-basedprivate network 103 in response to a request from the customer or inresponse to detecting that various hardware components have beenconnected to the network 412 at the customer's site 438. At this point,the lock on configuration changes may be removed and the customer maysubmit configuration changes for the radio-based private network 130,including updating the network plan 439, increasing the number of SIMs,increasing the number of cells, and so on. The RBPN management service424 may return a response to the customer indicating when the activationwill occur. Thereafter, the operation of the portion of the RBPNmanagement service 424 ends.

Turning now to FIG. 6 , shown is a flowchart that provides one exampleof the operation of a portion of the radio unit management service 427according to various embodiments. It is understood that the flowchart ofFIG. 6 provides merely an example of the many different types offunctional arrangements that may be employed to implement the operationof the portion of the radio unit management service 427 as describedherein. As an alternative, the flowchart of FIG. 6 may be viewed asdepicting an example of elements of a method implemented in thecomputing environment 403 (FIG. 4 ) according to one or moreembodiments.

Beginning with box 603, the radio unit management service 427 receivesan authentication request from a radio unit. For example, the radio unitmay have been shipped to a customer for use with the radio-based privatenetwork 103 (FIG. 1A), with some level of preconfiguration to contactthe radio unit management service 427. Upon being turned on and beingphysically connected to a network, the radio unit communicates with theradio unit management service 427 with the authentication request.

In box 606, the radio unit management service 427 determines thelocation of the radio unit. For example, the radio unit may present aset of coordinates (latitude and longitude) to the radio unit managementservice 427. The radio unit may include a Global Positioning System(GPS) or similar device in order to automatically determine a location.The radio unit may also provide a height.

In box 609, the radio unit management service 427 may communicate with aspectrum reservation service 410 (FIG. 4 ) in order to reserve spectrumfor use by the radio unit at the location. For example, the radio unitmanagement service 427 may send a request to reserve one or more CBRSfrequencies or television whitespace frequencies for the radio unit. Insome embodiments, the radio unit management service 427 may dynamicallyupdate one or more parameters stored on the radio unit so that the radiounit can communicate directly with the spectrum reservation service 410in order to reserve spectrum. For example, the radio unit managementservice 427 may establish or configure one or more parameters on theradio unit relating to channel bandwidth, frequencies, neighboring cellinformation, information to assist wireless devices 106 with roaming,and/or other parameters. The radio unit management service 427 mayconfigure the radio unit with one or more parameters that enable theradio unit to communicate with the spectrum reservation service 410.

In box 612, the radio unit management service 427 may configure one ormore endpoints for the core network 118 (FIG. 1A) on the radio unit.Such endpoints may be configured, for example, for the access mobilityfunction (AMF) or mobility management entity (MME) in the core network118. In other implementations where the radio unit is an access pointfor Wi-Fi-type networks, the radio unit management service 427 mayinstead configure the access point with certificate-based identitymanagement to manage connections. In box 615, the radio unit managementservice 427 activates the radio unit on the radio access network of theradio-based private network 103. Thereafter, the operation of theportion of the radio unit management service 427 ends.

With reference to FIG. 7 , shown is a schematic block diagram of thecomputing environment 403 according to an embodiment of the presentdisclosure. The computing environment 403 includes one or more computingdevices 700. Each computing device 700 includes at least one processorcircuit, for example, having a processor 703 and a memory 706, both ofwhich are coupled to a local interface 709. To this end, each computingdevice 700 may comprise, for example, at least one server computer orlike device. The local interface 709 may comprise, for example, a databus with an accompanying address/control bus or other bus structure ascan be appreciated.

Stored in the memory 706 are both data and several components that areexecutable by the processor 703. In particular, stored in the memory 706and executable by the processor 703 are the RBPN management API 423, theRBPN management service 424, the radio unit management service 427, andpotentially other applications. Also stored in the memory 706 may be adata store 415 and other data. In addition, an operating system may bestored in the memory 706 and executable by the processor 703.

It is understood that there may be other applications that are stored inthe memory 706 and are executable by the processor 703 as can beappreciated. Where any component discussed herein is implemented in theform of software, any one of a number of programming languages may beemployed such as, for example, C, C++, C#, Objective C, Java®,JavaScript®, Perl, PHP, Visual Basic®, Python®, Ruby, Flash®, or otherprogramming languages.

A number of software components are stored in the memory 706 and areexecutable by the processor 703. In this respect, the term “executable”means a program file that is in a form that can ultimately be run by theprocessor 703. Examples of executable programs may be, for example, acompiled program that can be translated into machine code in a formatthat can be loaded into a random access portion of the memory 706 andrun by the processor 703, source code that may be expressed in properformat such as object code that is capable of being loaded into a randomaccess portion of the memory 706 and executed by the processor 703, orsource code that may be interpreted by another executable program togenerate instructions in a random access portion of the memory 706 to beexecuted by the processor 703, etc. An executable program may be storedin any portion or component of the memory 706 including, for example,random access memory (RAM), read-only memory (ROM), hard drive,solid-state drive, USB flash drive, memory card, optical disc such ascompact disc (CD) or digital versatile disc (DVD), floppy disk, magnetictape, or other memory components.

The memory 706 is defined herein as including both volatile andnonvolatile memory and data storage components. Volatile components arethose that do not retain data values upon loss of power. Nonvolatilecomponents are those that retain data upon a loss of power. Thus, thememory 706 may comprise, for example, random access memory (RAM),read-only memory (ROM), hard disk drives, solid-state drives, USB flashdrives, memory cards accessed via a memory card reader, floppy disksaccessed via an associated floppy disk drive, optical discs accessed viaan optical disc drive, magnetic tapes accessed via an appropriate tapedrive, and/or other memory components, or a combination of any two ormore of these memory components. In addition, the RAM may comprise, forexample, static random access memory (SRAM), dynamic random accessmemory (DRAM), or magnetic random access memory (MRAM) and other suchdevices. The ROM may comprise, for example, a programmable read-onlymemory (PROM), an erasable programmable read-only memory (EPROM), anelectrically erasable programmable read-only memory (EEPROM), or otherlike memory device.

Also, the processor 703 may represent multiple processors 703 and/ormultiple processor cores and the memory 706 may represent multiplememories 706 that operate in parallel processing circuits, respectively.In such a case, the local interface 709 may be an appropriate networkthat facilitates communication between any two of the multipleprocessors 703, between any processor 703 and any of the memories 706,or between any two of the memories 706, etc. The local interface 709 maycomprise additional systems designed to coordinate this communication,including, for example, performing load balancing. The processor 703 maybe of electrical or of some other available construction.

Although the RBPN management API 423, the RBPN management service 424,the radio unit management service 427, and other various systemsdescribed herein may be embodied in software or code executed by generalpurpose hardware as discussed above, as an alternative the same may alsobe embodied in dedicated hardware or a combination of software/generalpurpose hardware and dedicated hardware. If embodied in dedicatedhardware, each can be implemented as a circuit or state machine thatemploys any one of or a combination of a number of technologies. Thesetechnologies may include, but are not limited to, discrete logiccircuits having logic gates for implementing various logic functionsupon an application of one or more data signals, application specificintegrated circuits (ASICs) having appropriate logic gates,field-programmable gate arrays (FPGAs), or other components, etc. Suchtechnologies are generally well known by those skilled in the art and,consequently, are not described in detail herein.

The flowcharts of FIGS. 5-6 show the functionality and operation of animplementation of portions of the RBPN management service 424 and theradio unit management service 427. If embodied in software, each blockmay represent a module, segment, or portion of code that comprisesprogram instructions to implement the specified logical function(s). Theprogram instructions may be embodied in the form of source code thatcomprises human-readable statements written in a programming language ormachine code that comprises numerical instructions recognizable by asuitable execution system such as a processor 703 in a computer systemor other system. The machine code may be converted from the source code,etc. If embodied in hardware, each block may represent a circuit or anumber of interconnected circuits to implement the specified logicalfunction(s).

Although the flowcharts of FIGS. 5-6 show a specific order of execution,it is understood that the order of execution may differ from that whichis depicted. For example, the order of execution of two or more blocksmay be scrambled relative to the order shown. Also, two or more blocksshown in succession in FIGS. 5-6 may be executed concurrently or withpartial concurrence. Further, in some embodiments, one or more of theblocks shown in FIGS. 5-6 may be skipped or omitted. In addition, anynumber of counters, state variables, warning semaphores, or messagesmight be added to the logical flow described herein, for purposes ofenhanced utility, accounting, performance measurement, or providingtroubleshooting aids, etc. It is understood that all such variations arewithin the scope of the present disclosure.

Also, any logic or application described herein, including the RBPNmanagement API 423, the RBPN management service 424, and the radio unitmanagement service 427, that comprises software or code can be embodiedin any non-transitory computer-readable medium for use by or inconnection with an instruction execution system such as, for example, aprocessor 703 in a computer system or other system. In this sense, thelogic may comprise, for example, statements including instructions anddeclarations that can be fetched from the computer-readable medium andexecuted by the instruction execution system. In the context of thepresent disclosure, a “computer-readable medium” can be any medium thatcan contain, store, or maintain the logic or application describedherein for use by or in connection with the instruction executionsystem.

The computer-readable medium can comprise any one of many physical mediasuch as, for example, magnetic, optical, or semiconductor media. Morespecific examples of a suitable computer-readable medium would include,but are not limited to, magnetic tapes, magnetic floppy diskettes,magnetic hard drives, memory cards, solid-state drives, USB flashdrives, or optical discs. Also, the computer-readable medium may be arandom access memory (RAM) including, for example, static random accessmemory (SRAM) and dynamic random access memory (DRAM), or magneticrandom access memory (MRAM). In addition, the computer-readable mediummay be a read-only memory (ROM), a programmable read-only memory (PROM),an erasable programmable read-only memory (EPROM), an electricallyerasable programmable read-only memory (EEPROM), or other type of memorydevice.

Further, any logic or application described herein, including the RBPNmanagement API 423, the RBPN management service 424, and the radio unitmanagement service 427, may be implemented and structured in a varietyof ways. For example, one or more applications described may beimplemented as modules or components of a single application. Further,one or more applications described herein may be executed in shared orseparate computing devices or a combination thereof. For example, aplurality of the applications described herein may execute in the samecomputing device 700, or in multiple computing devices 700 in the samecomputing environment 403.

Disjunctive language such as the phrase “at least one of X, Y, or Z,”unless specifically stated otherwise, is otherwise understood with thecontext as used in general to present that an item, term, etc., may beeither X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z).Thus, such disjunctive language is not generally intended to, and shouldnot, imply that certain embodiments require at least one of X, at leastone of Y, or at least one of Z to each be present.

It should be emphasized that the above-described embodiments of thepresent disclosure are merely possible examples of implementations setforth for a clear understanding of the principles of the disclosure.Many variations and modifications may be made to the above-describedembodiment(s) without departing substantially from the spirit andprinciples of the disclosure. All such modifications and variations areintended to be included herein within the scope of this disclosure andprotected by the following claims.

Therefore, the following is claimed:
 1. A system, comprising: a cloud provider network including a plurality of regions; and at least one computing device in the cloud provider network implementing a private 5G network management service configured to at least: receive a request via an interface from a customer to create a private 5G network for the customer, the request specifying a quantity of wireless devices that will connect to the private 5G network; determine a quantity of radio units for the private 5G network based at least in part on the quantity of wireless devices; preconfigure a plurality of radio units corresponding to the quantity of radio units to implement a radio access network for the private 5G network; preconfigure a plurality of subscriber identity modules (SIMs) corresponding to the quantity of wireless devices for the radio access network; initiate a shipment to the customer of the plurality of radio units and the plurality of SIMS that have been preconfigured; determine a particular region of the plurality of regions based at least in part on at least one of: a specification of the particular region by the customer, or a network latency between the radio access network and the particular region; and provision one or more resources in the particular region of the plurality of regions of the cloud provider network to function as a core network for the private 5G network.
 2. The system of claim 1, wherein the at least one computing device is further configured to at least configure one or more parameters on a particular radio unit of the plurality of radio units to cause the particular radio unit to reserve frequency spectrum from a spectrum registration service for the particular radio unit based at least in part on a location of the particular radio unit.
 3. The system of claim 1, wherein the request specifies a measure of edge computing capacity to be provided in the private 5G network.
 4. The system of claim 1, wherein the private 5G network management service is further configured to at least provision a virtual network link for control plane network traffic from the radio access network to the one or more resources in the particular region.
 5. A computer-implemented method, comprising: receiving a request via an interface to create a radio-based private network for a customer, the request indicating a quantity of wireless devices that will connect to the radio-based private network; determining a quantity of a plurality of radio units to serve the radio-based private network based at least in part on the quantity of wireless devices; preconfiguring the plurality of radio units to implement a radio access network for the radio-based private network; initiating a shipment to the customer of the plurality of radio units that have been preconfigured; determining a particular region of a plurality of regions in a cloud provider network based at least in part on at least one of: a specification of the particular region in the request, or a network latency between the radio access network and the particular region; and provisioning one or more resources in the particular region of the cloud provider network to function as a core network for the radio-based private network.
 6. The computer-implemented method of claim 5, wherein the request further indicates a measure of edge computing capacity requested for the radio-based private network, and the method further comprises: preconfiguring at least one computing device to provide the edge computing capacity in the radio-based private network as a provider substrate extension of the cloud provider network; and initiating a shipment to the customer of the at least one computing device.
 7. The computer-implemented method of claim 6, further comprising: preconfiguring the at least one computing device to implement at least one radio access network function for one or more of the plurality of radio units; and preconfiguring the at least one computing device to communicate with the one or more resources in the cloud provider network that function as the core network.
 8. The computer-implemented method of claim 5, further comprising reserving radio spectrum for the radio-based private network via a spectrum reservation service based at least in part on a location specified in the request.
 9. The computer-implemented method of claim 5, further comprising provisioning a virtual network link for control plane network traffic from the radio access network to the one or more resources in the particular region.
 10. The computer-implemented method of claim 9, further comprising configuring the radio access network such that a loss of connectivity via the virtual network link does not initially impact connectivity in the radio access network for one or more connections between the quantity of wireless devices of the radio access network.
 11. The computer-implemented method of claim 5, further comprising initiating a shipment to the customer of a plurality of subscriber identity modules (SIMs) preconfigured for the radio-based private network for the quantity of wireless devices.
 12. The computer-implemented method of claim 5, further comprising: receiving a request via the interface to create a location for deployment of the radio-based private network for the customer at an address; generating a unique location identifier based at least in part on the address; returning the unique location identifier to the customer via the interface; and wherein the request to create the radio-based private network specifies the unique location identifier.
 13. The computer-implemented method of claim 5, further comprising: authenticating the customer for access to an account through a cloud service provider that operates the cloud provider network; and verifying that the account has permission to create the radio-based private network.
 14. A non-transitory computer-readable medium embodying a program executable in at least one computing device, wherein when executed the program causes the at least one computing device to at least: receive a request via an interface to create a radio-based private network for a customer, the request indicating a network plan, the network plan including a quantity of wireless devices that will connect to the radio-based private network and a quantity of radio units for the radio-based private network; preconfigure a plurality of radio units corresponding to the quantity of radio units to implement a radio access network for the radio-based private network; preconfigure a plurality of subscriber identity modules (SIMs) corresponding to the quantity of wireless devices for the radio access network; initiate a shipment to the customer of the plurality of radio units and the plurality of SIMs that have been preconfigured; determine a particular region of a plurality of regions of a cloud provider network based at least in part on at least one of: a specification of the particular region in the request, or a network latency between the radio access network and the particular region; and provision one or more resources in the particular region of the cloud provider network to function as a core network for the radio-based private network.
 15. The non-transitory computer-readable medium of claim 14, wherein the interface corresponds to an application programming interface (API).
 16. The non-transitory computer-readable medium of claim 14, wherein the interface corresponds to a graphical user interface.
 17. The non-transitory computer-readable medium of claim 14, wherein when executed the program further causes the at least one computing device to at least: generate an order for one or more of the plurality of radio units; and transmitting the order for the one or more of the plurality of radio units to one or more vendor computing devices.
 18. The non-transitory computer-readable medium of claim 17, wherein when executed the program further causes the at least one computing device to at least receive a listing of serial numbers corresponding to the one or more of the plurality of radio units from the one or more vendor computing devices.
 19. The non-transitory computer-readable medium of claim 14, wherein when executed the program further causes the at least one computing device to at least prevent a change to a configuration of the radio-based private network via the interface until the shipment is delivered.
 20. The non-transitory computer-readable medium of claim 14, wherein when executed the program further causes the at least one computing device to at least: receive an authentication request from a particular radio unit of the plurality of radio units; determine a location of the particular radio unit; reserve frequency spectrum from a spectrum registration service for the particular radio unit based at least in part on the location; and configure one or more endpoints for the core network on the particular radio unit. 